Repository navigation
Conversation
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #307 and durable-workflow/.github#232.
Preserve Python's recorded wait-for-all timing when parallel-group policy is absent, while preparing first-recorded-failure replay for explicitly admitted
propagategroups.The initial draft pins a legacy partial history: the higher-position activity has failed while its lower-position sibling is still open, and the failure handler must remain suspended. A second control preserves positional failure selection once the remaining sibling settles. The fixture runs through the ordinary replay corpus.
Workflow acknowledged the bounded contract/fixture handoff on #232 and fixed the discriminator placement. The explicit-policy implementation follows on this branch behind disabled capability admission. Worker advertisement, live negotiation and publication remain off until the producer contract and installed runtime support are qualified. Workflow and Server retain their producer implementations.